Method and apparatus for configuring priority of uci

ABSTRACT

A method for wireless communication performed by a user equipment (UE) is provided. The method includes receiving, from a base station (BS), a Radio Resource Control (RRC) configuration to configure a first semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) and generating first uplink control information (UCI) in response to the first SPS PDSCH, where the RRC configuration includes a first parameter that indicates a priority of the first UCI.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present disclosure claims the benefit of and priority of provisionalU.S. Patent Application Ser. No. 62/866,796, filed on Jun. 26, 2019,entitled “Method and apparatus for handling impact on introduction ofnew physical identification” (“the '796 provisional”). The disclosure ofthe '796 provisional is hereby incorporated fully by reference into thepresent disclosure.

FIELD

The present disclosure is related to wireless communication, and moreparticularly, to a method for configuring priority of uplink controlinformation (UCI) in cellular wireless communication networks.

BACKGROUND

Various efforts have been made to improve different aspects of wirelesscommunication for cellular wireless communication systems, such as fifthgeneration (5G) New Radio (NR) by improving data rate, latency,reliability, and mobility. In NR Technical Specification (TS) Release 15(Rel-15), a modulation and coding scheme (MCS) MCS table (e.g.,qam64lowSE) is introduced to schedule a more reliable data transmission.For grant-based physical downlink shared channel (PDSCH) transmissions,there are two ways to configure the qam64lowSE table. One is byextending an existing radio resource control (RRC) parameter mcs-Tablein a PDSCH configuration (e.g., PDSCH-Config), and the other one is byconfiguring an MCS cell radio network temporary identifier (C-RNTI)(MCS-C-RNTI). For downlink (DL) semi-persistent scheduling (SPS)transmissions, only the RRC parameter mcs-Table in a SPS configuration(e.g., SPS-Config) can indicate whether or not the qam64lowSE table isconfigured. Furthermore, in NR Rel-15, a user equipment (UE) does notexpect to transmit more than one physical uplink control channel (PUCCH)with hybrid automatic repeat request acknowledgement (HARQ-ACK)information in a slot. Thus, in Rel-15 there is no need to considermultiplexing, prioritization, or collision behavior on HARQ-ACKtransmission for different service types within a slot for a UE. Thedifferent service types supported in 5G NR include enhanced MobileBroadband (eMBB) and Ultra-Reliable Low-Latency Communication (URLLC).However, in Rel-16 and later releases, UCI messages may fully orpartially overlap within a slot. The multiple UCI messages may includeUCI for grant-based PDSCH transmissions and/or UCI for the SPS PDSCHtransmissions. Therefore, there is a need for an improved and efficientmechanism for a UE to handle UCI collision within a slot.

SUMMARY

The present disclosure is related to a method performed by a UE incellular wireless communication network for configuring the priority ofthe UCI.

According to an aspect of the present disclosure, a UE is provided thatincludes one or more non-transitory computer-readable media containingcomputer-executable instructions embodied therein and at least oneprocessor coupled to the one or more non-transitory computer-readablemedia. The at least one processor is configured to execute thecomputer-executable instructions to receive, from a BS, an RRCconfiguration to configure a first SPS PDSCH, and generate first UCI inresponse to the first SPS PDSCH, where the RRC configuration includes afirst parameter that indicates a priority of the first UCI.

According to another aspect of the present disclosure, a method forwireless communication performed by a UE is provided. The methodincludes receiving, from a BS, an RRC configuration to configure a firstSPS PDSCH, and generating first UCI in response to the first SPS PDSCH,where the RRC configuration includes a first parameter that indicates apriority of the first UCI.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the disclosure are best understood from the followingdetailed description when read with the accompanying drawings. Variousfeatures are not drawn to scale. Dimensions of various features may bearbitrarily increased or reduced for clarity of discussion.

FIG. 1 is a flowchart of a method performed by a UE for configuring apriority of UCI for an SPS PDSCH according to an example implementationof the present disclosure.

FIG. 2 is a flowchart of a method performed by a UE for configuring apriority of UCI for a dynamic PDSCH according to an exampleimplementation of the present disclosure.

FIG. 3 is a diagram illustrating a procedure for handling UCI collisionaccording to an example implementation of the present disclosure.

FIG. 4 is a block diagram illustrating a node for wireless communicationin accordance with various aspects of the present disclosure.

DESCRIPTION

The following description contains specific information related toimplementations of the present disclosure. The drawings and theiraccompanying detailed description are merely directed toimplementations. However, the present disclosure is not limited to theseimplementations. Other variations and implementations of the presentdisclosure will be obvious to those skilled in the art.

Unless noted otherwise, like or corresponding elements among thedrawings may be indicated by like or corresponding reference numerals.Moreover, the drawings and illustrations in the present disclosure aregenerally not to scale and are not intended to correspond to actualrelative dimensions.

For the purpose of consistency and ease of understanding, like featuresmay be identified (although, in some examples, not shown) by the samenumerals in the drawings. However, the features in differentimplementations may be differed in other respects and shall not benarrowly confined to what is shown in the drawings.

The phrases “in one implementation,” or “in some implementations,” mayeach refer to one or more of the same or different implementations. Theterm “coupled” is defined as connected whether directly or indirectlythrough intervening components and is not necessarily limited tophysical connections. The term “comprising” means “including, but notnecessarily limited to” and specifically indicates open-ended inclusionor membership in the so-described combination, group, series orequivalent. The expression “at least one of A, B and C” or “at least oneof the following: A, B and C” means “only A, or only B, or only C, orany combination of A, B and C.”

The terms “system” and “network” may be used interchangeably. The term“and/or” is only an association relationship for describing associatedobjects and represents that three relationships may exist such that Aand/or B may indicate that A exists alone, A and B exist at the sametime, or B exists alone. The character “/” generally represents that theassociated objects are in an “or” relationship.

For the purposes of explanation and non-limitation, specific detailssuch as functional entities, techniques, protocols, and standards areset forth for providing an understanding of the disclosed technology. Inother examples, detailed description of well-known methods,technologies, systems, and architectures are omitted so as not toobscure the description with unnecessary details.

Persons skilled in the art will immediately recognize that any networkfunction(s) or algorithm(s) disclosed may be implemented by hardware,software or a combination of software and hardware. Disclosed functionsmay correspond to modules which may be software, hardware, firmware, orany combination thereof.

A software implementation may include computer executable instructionsstored on a computer readable medium such as memory or other type ofstorage devices. One or more microprocessors or general-purposecomputers with communication processing capability may be programmedwith corresponding executable instructions and perform the disclosednetwork function(s) or algorithm(s).

The microprocessors or general-purpose computers may includeApplications Specific Integrated Circuitry (ASIC), programmable logicarrays, and/or using one or more Digital Signal Processor (DSPs).Although some of the disclosed implementations are oriented to softwareinstalled and executing on computer hardware, alternativeimplementations implemented as firmware or as hardware or combination ofhardware and software are well within the scope of the presentdisclosure. The computer readable medium includes but is not limited toRandom Access Memory (RAM), Read Only Memory (ROM), ErasableProgrammable Read-Only Memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), flash memory, Compact DiscRead-Only Memory (CD-ROM), magnetic cassettes, magnetic tape, magneticdisk storage, or any other equivalent medium capable of storingcomputer-readable instructions.

A radio communication network architecture such as a Long Term Evolution(LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Prosystem, or a 5G NR Radio Access Network (RAN) typically includes atleast one base station (BS), at least one UE, and one or more optionalnetwork elements that provide connection within a network. The UEcommunicates with the network such as a Core Network (CN), an EvolvedPacket Core (EPC) network, an Evolved Universal Terrestrial RAN(E-UTRAN), a 5G Core (5GC), or an internet via a RAN established by oneor more BSs.

A UE may include but is not limited to a mobile station, a mobileterminal or device, or a user communication radio terminal. The UE maybe portable radio equipment that includes but is not limited to a mobilephone, a tablet, a wearable device, a sensor, a vehicle, or a PersonalDigital Assistant (PDA) with wireless communication capability. The UEis configured to receive and transmit signals over an air interface toone or more cells in a RAN.

A BS may be configured to provide communication services according to atleast a Radio Access Technology (RAT) such as Worldwide Interoperabilityfor Microwave Access (WiMAX), Global System for Mobile communications(GSM) that is often referred to as 2G, GSM Enhanced Data rates for GSMEvolution (EDGE) RAN (GERAN), General Packet Radio Service (GPRS),Universal Mobile Telecommunication System (UMTS) that is often referredto as 3G based on basic wideband-code division multiple access (W-CDMA),high-speed packet access (HSPA), LTE, LTE-A, evolved LTE (eLTE) that isLTE connected to 5GC, NR (often referred to as 5G), and/or LTE-A Pro.However, the scope of the present disclosure is not limited to theseprotocols.

A BS may include but is not limited to a node B (NB) in the UMTS, anevolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC)in UMTS, a BS controller (BSC) in the GSM/GERAN, a ng-eNB in an E-UTRABS in connection with 5GC, a next generation Node B (gNB) in the 5G-RAN,or any other apparatus capable of controlling radio communication andmanaging radio resources within a cell. The BS may serve one or more UEsvia a radio interface.

The BS is operable to provide radio coverage to a specific geographicalarea using a plurality of cells forming the RAN. The BS supports theoperations of the cells. Each cell is operable to provide services to atleast one UE within its radio coverage.

Each cell (often referred to as a serving cell) provides services toserve one or more UEs within its radio coverage such that each cellschedules the downlink (DL) and optionally uplink (UL) resources to atleast one UE within its radio coverage for DL and optionally UL packettransmissions. The BS can communicate with one or more UEs in the radiocommunication system via the plurality of cells.

A cell may allocate sidelink (SL) resources for supporting ProximityService (ProSe) or Vehicle to Everything (V2X) service. Each cell mayhave overlapped coverage areas with other cells.

As discussed previously, the frame structure for NR supports flexibleconfigurations for accommodating various next generation (e.g., 5G)communication requirements such as Enhanced Mobile Broadband (eMBB),Massive Machine Type Communication (mMTC), and Ultra-Reliable andLow-Latency Communication (URLLC), while fulfilling high reliability,high data rate and low latency requirements. The OrthogonalFrequency-Division Multiplexing (OFDM) technology in the 3rd GenerationPartnership Project (3GPP) may serve as a baseline for an NR waveform.The scalable OFDM numerology such as adaptive sub-carrier spacing,channel bandwidth, and Cyclic Prefix (CP) may also be used.

Two coding schemes are considered for NR, specifically Low-DensityParity-Check (LDPC) code and Polar Code. The coding scheme adaption maybe configured based on channel conditions and/or service applications.

At least DL transmission data, a guard period, and uplink (UL)transmission data should be included in a transmission time interval(TTI) of a single NR frame. The respective portions of the DLtransmission data, the guard period, and the UL transmission data shouldalso be configurable based on, for example, the network dynamics of NR.Sidelink resources may also be provided in an NR frame to support ProSeservices or V2X services.

Since at least two HARQ-ACK codebooks for supporting different servicetypes may be simultaneously constructed for a UE, a physicalidentification for identifying a HARQ-ACK codebook may be necessary. Forgrant-based PDSCH, a new-RNTI may be the physical identification to helpdifferentiate HARQ-ACK codebooks for different service types. In otherwords, the PDSCH transmission scheduled by a DL control information(DCI) scrambled with the new-RNTI may be regarded as the transmissionwith high priority, which may be linked to a specific HARQ-ACK codebookwith a low-latency feedback. For a grant-based physical UL sharedchannel (PUSCH), the new-RNTI may be the identification to identify thebehavior of UCI multiplexing. It should be noted that the presentdisclosure does not preclude other possible physical identifications.However, introducing the new-RNTI may lead to some impact on configuringthe qam64lowSE table.

Possible impacts may include: a prioritized PDSCH or PUSCH transmissionmay be configured with the qam64lowSE low spectral efficiency tableusing RRC only signalling because configuration using the MCS-C-RNTI maynot be usable; it may be too restrictive if a prioritized PDSCHtransmission implies being configured with the qam64lowSE table becauselow latency services are not necessarily associated with highreliability; the physical identification for identifying HARQ-ACKfeedback between grant-based PDSCH/PUSCH and DL SPS PDSCH/UL configuredgrant (CG) may remain unclear.

Based on the above-mentioned new-RNTI approach, scheduling theqam64lowSE table without the MCS-C-RNTI may need to be specified.Moreover, how to maintain the flexibility of scheduling different MCStables upon receiving an assignment/grant indicated by a physicaldownlink control channel (PDCCH) scrambled with the new-RNTI may need tobe clarified as well. Furthermore, a UE may validate or initiate a DLSPS assignment PDCCH or configured UL grant Type 2 PDCCH if the cyclicredundancy check (CRC) of the corresponding DCI is scrambled with aconfigured scheduling (CS) RNTI (CS-RNTI) and a new data indicator (NDI)field for the enabled transport block (TB) is set to zero. Thus, thepriority of the SPS PDSCH reception or configured UL grant may not beidentified based on the new-RNTI. Therefore, the general behavior of thephysical identification for identifying the HARQ-ACK codebooks fordifferent service types, grant based PDSCH, SPS PDSCH, and their ULcounterparts may need to be specified. A physical identification may bea new DCI format, a new RNTI, or a new field in a DCI format. It shouldbe noted that the present disclosure does not preclude other possiblephysical identifications (e.g., a new DCI field, a dedicated searchspace set, a new DCI format) for dynamically scheduling the MCS table.

Case 1: New RNTI for Priority Indication Upon Dynamic MCS TableAdaptation

In one implementation, a new-RNTI may be introduced as the physicalidentification for identifying the HARQ-ACK codebooks for differentservice types. In one implementation, a PUSCH transmission scheduled bya DCI with CRC bits scrambled by the new-RNTI may indicate whether ornot UCI multiplexing on PUSCH is allowed. For example, if a PUSCHtransmission is scheduled by a DCI scrambled with the new-RNTI, no UCIis allowed to be multiplexed on the PUSCH in one implementation, whereasonly UCI corresponding to a PDSCH scheduled by the DCI scrambled withthe new-RNTI is allowed to be multiplexed on the PUSCH in anotherimplementation. It should be noted that the new-RNTI may be aUE-specific RNTI that is applicable for a cell group or a transmissionreception point (TRP) group configured for the UE. Several mechanisms toconfigure the qam64lowSE table or other tables that may possibly beintroduced in the future upon the new-RNTI are disclosed below.

Case 1-1: Combine RRC Parameter Mcs-Table in PDSCH-Config, PUSCH-Config,SPS-Config or ConfiguredGrantConfig with Some Conditions of TransportBlock Size (TBS)/Duration/Number of Physical Resource Block (PRB) of theData Transmission

For the PDSCH or PUSCH scheduled by a PDCCH with a DCI format with CRCscrambled by the new-RNTI or for the PDSCH or PUSCH scheduled withoutcorresponding PDCCH transmission, a higher layer PDSCH configurationSPS-Config or PUSCH configuration ConfiguredGrantConfig is used:

Case 1-1-1: If the higher layer parameter mcs-Table given byPDSCH-Config, PUSCH-Config, SPS-Config or ConfiguredGrantConfig is setto ‘qam64LowSE’ or other tables for configuring data transmission with alow block error rate (BLER) requirement, the UE may check whether or notthe TBS or the PDSCH/PUSCH duration or the number of allocated PRBs forthe PDSCH/PUSCH is larger than a pre-defined or configured thresholdvalue (e.g., configured via RRC signalling).

In one implementation, a configured threshold value for the PDSCH/PUSCHduration may be the number of symbols or the number of sub-slots. Asub-slot may include multiple symbols within a slot. Considering thatdata transmission indicated as high priority may not necessarily have ahigh reliability requirement, the data with a larger TBS, or a longerduration, or larger PRB number, or a combination of the above factors,may be regarded as a transmission that requires a high data rate.

In one implementation, if the TBS/duration/PRB number of the datatransmission is larger than the threshold value, the UE may use an MCSindex (e.g., I_(MCS)) and the 64QAM table (e.g., Table 5.1.3.1-1 in TS38.214) to determine a modulation order and a target code rate used inthe PDSCH or PUSCH; otherwise, the UE may follow the table configuredusing higher layer parameters (e.g., Table 5.1.3.1-3 in TS 38.214).

In another implementation, more MCS tables (for example, the 256QAMtable in Table 5.1.3.1-2 in TS 38.214) may be considered and multiplethreshold values are introduced. The threshold values may define theapplicable range of individual MCS tables.

Case 1-1-2: If the higher layer parameter mcs-Table given byPDSCH-Config, PUSCH-Config, SPS-Config or ConfiguredGrantConfig isabsent or the higher layer parameter mcs-Table given by PDSCH-Config,PUSCH-Config, SPS-Config or ConfiguredGrantConfig is set to ‘qam256’,the UE may check whether or not the TBS or the PDSCH/PUSCH duration orthe number of allocated PRBs of a data transmission is smaller than apre-defined threshold value or a configured threshold value (e.g.,configured via RRC signalling).

In one implementation, a configured threshold value for the PDSCH/PUSCHduration may be the number of symbols or the number of sub-slots.Considering that data transmission indicated as high priority may alsohave a high reliability requirement, the data with a smaller TBS, or ashorter duration, or a smaller PRB number, or a combination of the abovefactors, may be regarded as a transmission that requires highreliability.

In one implementation, if the TBS/duration/PRB number of the datatransmission is smaller than the threshold value, the UE may use I_(MCS)and the qam64lowSE table (e.g. Table 5.1.3.1-3 in TS 38.214) or othertables for configuring a data transmission with a low BLER requirementto determine a modulation order and a target code rate used in the PDSCHor PUSCH; else, the UE may use the 64QAM table (e.g. Table 5.1.3.1-1 inTS 38.214).

Case 1-2: Handling of Medium Access Control (MAC) Control Elements (CEs)

Case 1-2-1: The network may indicate an MCS table for the PDSCH and/orPUSCH of a serving cell by sending an MCS table indication via aUE-specific PDSCH/PUSCH MAC CE. A UE-specific PDSCH/PUSCH MAC CE for theMCS table indication may be a specific indication to inform a UE whichMCS table should be used. When the UE receives the MAC CE, the UE mayapply a corresponding indication to the PDSCH/PUSCH transmission. In oneimplementation, respective MAC CE commands are provided for respectiveDL PDSCH and UL PUSCH transmission. In another implementation, a singleMAC-CE command applies to both PDSCH and PUSCH.

In one implementation, when the UE receives the MCS table indication viaUE-specific PDSCH/PUSCH MAC CE from the network, the MAC entity of theUE may implicitly indicate to lower layers the information regarding theMCS table indication for a UE-specific PDSCH/PUSCH MAC CE. In otherwords, the MCS table indication may include the range of applicable MCS(e.g., maximum applicable MCS and minimum applicable MCS; up to 64QAM or256QAM) or the allowed MCS configuration instead of providing a specificinstruction of an applied MCS table.

In one implementation, the MCS table indication received via theUE-specific PDSCH/PUSCH MAC CE may be identified by a MAC protocol dataunit (PDU) subheader with a logical channel identifier (LCD). The MAC CEmay have a variable size with following fields and may include eitherone or any combination of the information as provided below:

-   -   TRP ID: This field contains the TRP-Id of the TRP to which the        MAC CE applies.    -   CORESET ID: This field contains the CORESET-Id of the control        resource set (CORESET) containing scheduling information of the        data channel to which the MAC CE applies.    -   Serving Cell ID: This field indicates the identity of the        serving cell to which the MAC CE applies.    -   BWP ID: This field contains BWP-Id of a DL/UL bandwidth part        (BWP) to which the MAC CE applies.    -   MCS table ID: This field indicates the MCS table identified by        mcs-Table or mcs-Table-Id.    -   PDSCH/SPS: This field indicates whether the MCS table indication        is for dynamic PDSCH scheduling or SPS scheduling.    -   PUSCH/Configured grant: This field indicates whether the MCS        table indication is for dynamic PUSCH scheduling or configured        grant scheduling.    -   PDSCH/PUSCH: This field indicates whether the MCS table        indication is for the PDSCH or PUSCH.    -   SPS configuration ID: This field indicates to which SPS        configuration the MCS table indication is applied.    -   Configured grant configuration ID: This field indicates to which        configured grant configuration the MCS table indication is        applied.

The mcs-Table parameter in PDSCH-Config, PUSCH-Config, SPS-Config orConfiguredGrantConfig may be an integer to identify which table isapplied, or an information element (IE) mcs-Table-Id may be configured.It should be noted that from the UE's perspective, the IE mcs-Table-Idmay be cell specific, cell group specific or TRP specific. In addition,an MCS table index may be associated with a specific MCS table. Forexample, index 0 may refer to the 64QAM table, index 1 may refer to the256QAM table, and index 2 may refer to the qam64lowSE table.

Case 1-2-2: The network may indicate an MCS table for the PDSCH (of aBWP and/or of a serving cell and/or a TRP) using higher layerparameters, and the parameter may be activated/deactivated by an MCStable Activation/Deactivation MAC CE. For example, if the activationstatus is verified and the MCS table is configured by the higher layer,the UE may apply the MCS table configured using the higher layer;otherwise the UE may use the default MCS table (for example, the 64QAMtable). It should be noted that if a higher layer parameter (e.g.,mcs-table) is absent, the UE may use the default MCS table regardless ofthe status of Activation/Deactivation MAC CE. In one implementation, thedefault MCS table may be the 64QAM table if the parameter mcs-table isabsent. In one implementation, the default MCS table may be qam64LowSEtable based upon the new-RNTI.

In one implementation, the MCS table Activation/Deactivation MAC CE maybe identified by a MAC PDU subheader with an LCID. In oneimplementation, the MAC CE may have a fixed size of zero bit. In anotherimplementation, the MAC CE may have a variable size with followingfields to indicate the activation/deactivation status for different BWPsand/or different cells and/or different TRPs. The MAC CE may includeeither one or any combination of the information as provided below:

-   -   Activation/Deactivation: This field indicates the        activation/deactivation status for the MCS table.    -   TRP ID: This field contains TRP-Id of the TRP to which the MAC        CE applies.    -   CORESET ID: This field contains CORESET-Id of the CORESET        containing scheduling information of the data channel to which        the MAC CE applies.    -   Serving Cell ID: This field indicates the identity of the        Serving Cell to which MAC CE applies.    -   BWP ID: This field contains BWP-Id of a DL BWP to which MAC CE        applies.    -   MCS table ID: This field indicates the MCS table identified by        mcs-Table or mcs-Table-Id.    -   PDSCH/SPS: This field indicates whether the MCS table indication        is for dynamic PDSCH scheduling or SPS scheduling.    -   PUSCH/Configured grant: This field indicates whether the MCS        table indication is for dynamic PUSCH scheduling or configured        grant scheduling.    -   PDSCH/PUSCH: This field indicates whether the MCS table        indication is for the PDSCH or PUSCH.    -   SPS configuration ID: This filed indicates to which SPS        configuration the MCS table indication is applied.    -   Configured grant configuration ID: This field indicates to which        configured grant configuration the MCS table indication is        applied.

Case 1-2-3: The network may indicate an MCS table for the PDSCH (of aBWP and/or a serving cell and/or a TRP) using higher layer parameters.However, if the UE receives the MAC CE indication that indicates whichMCS table should be applied, the UE may use the MCS table indicated bythe MAC CE. For example, if the qam64lowSE table is configured bymcs-Table in PDSCH-Config, PUSCH-Config, SPS-Config orConfiguredGrantConfig and the UE receives an MAC CE that indicates the64QAM table, the UE may apply the 64QAM table to, for example, thePDSCH, PUSCH, the SPS PDSCH, or the CG PUSCH depending on which channelis indicated by the MAC CE. Also, MAC CE for MCS table indication may beapplied when reconfiguration occurs. In other words, the priority of theMAC CE indication for the MCS table may be higher than the signallingfrom the RRC configuration for the MCS table.

Case 2: Priority Differentiation of Corresponding UCI BetweenGrant-Based PDSCH (e.g., PDSCH) and Grant-Free PDSCH (e.g., SPS PDSCH)

Several mechanisms for handling collision between UCI for grant-basedPDSCH (e.g., HARQ-ACK information for the PDSCH) and UCI for grant-freePDSCH (e.g., HARQ-ACK information for the SPS PDSCH) with differentpriorities are provided below. It should be noted that the UCI may betransmitted on the PUCCH or PUSCH transmission. In one implementation,UCI transmitted by the UE may include the HARQ-ACK information inresponse to a PDSCH or a SPS PDSCH. It should be noted that “atransmission with high priority” or “a transmission is prioritized overother transmissions” in the present disclosure may mean a transmissionthat is transmitted by the UE when multiple transmissions overlap in thetime domain (e.g., partial or full time domain resource allocationbetween different transmissions may be configured in the same symbol).Transmissions other than the one being identified as high priority maynot be transmitted. In the following cases, the priority of UCI for thePDSCH may be identified by the new-RNTI (e.g., UCI corresponding to thePDSCH with CRC scrambled by the new-RNTI may be regarded as highpriority) or by other physical identifications (e.g., a DCI field, a newDCI format).

Case 2-1: Collision Between UCI for PDSCH Scheduled by DCI with CRCScrambled by the New-RNTI and UCI for the SPS PDSCH Identified as aTransmission with High Priority

In one implementation, UCI for the PDSCH and UCI for the SPS PDSCH mayboth be identified as high priority transmissions using differentphysical identifications. In one implementation, UCI for the PDSCH maybe identified as high priority using the new-RNTI and UCI for the SPSPDSCH may be identified as the transmission with high priority among UCIfor overlapped multiple active SPS PDSCHs. In other words, UCI for thePDSCH scheduled by DCI with CRC scrambled by the new-RNTI may beregarded as high priority transmission when collision occurs between UCIfor the PDSCH with the new-RNTI and UCI for the PDSCH with C-RNTI orMCS-C-RNTI in case 2-1.

Case 2-1-1: In one implementation, the priority of UCI for a dynamicallyscheduled PDSCH (e.g., PDSCH) may always be regarded as higher than thepriority of UCI for an SPS PDSCH since the priority between the PDSCHand SPS PDSCH has not been specified. For example, when collision occursbetween UCI for the PDSCH and UCI for the SPS PDSCH, the UCI for thePDSCH may be prioritized. In one implementation, although the UCI forthe PDSCH and SPS PDSCH are both identified as high prioritytransmissions (e.g., the PDSCH and the SPS PDSCH may use differentphysical identifications to indicate priority), the UCI corresponding tothe PDSCH may always be prioritized over the UCI corresponding to SPSPDSCH when collision occurs.

Case 2-1-2: In one implementation, multiple active SPS configurationsmay be supported, and each SPS configuration may have a correspondingindex. An SPS PDSCH corresponding to a specific index may be regarded asthe prioritized PDSCH. In one implementation, an SPS PDSCH with aspecific index (e.g., index 0) among multiple active SPS PDSCHs may beprioritized over other SPS PDSCHs with other indexes when collisionoccurs. In one implementation, the SPS PDSCH corresponding to aconfiguration with index 0 may be the prioritized SPS PDSCH, and UCI forthe SPS PDSCH configured with index 0 may be prioritized when collisionoccurs between UCI for the PDSCH and the UCI for the SPS PDSCH withindex 0. In one implementation, the SPS PDSCH corresponding to aconfiguration with index 0 may be the prioritized SPS PDSCH amongmultiple active SPS PDSCHs if multiple active SPS PDSCHs overlap, andthe UCI for the SPS PDSCH configured with index 0 may have the samepriority as UCI for the PDSCH when collision occurs. In oneimplementation, both the UCI for the SPS PDSCH with index 0 and the UCIfor the PDSCH may be regarded as high priority transmissions, and thepriority between the UCIs may not be necessary.

Case 2-1-3: In one implementation, a priority of UCI for an SPS PDSCHmay be configured by a parameter in an SPS configuration (e.g.,SPS-Config). In one implementation, if the specific parameter foridentifying the priority is configured in SPS-Config, UCI for the SPSPDSCH corresponding to the SPS-Config with the specific parameter may beprioritized when collision occurs between UCI for dynamic PDSCH and theUCI for the SPS PDSCH. In one implementation, the configured parametermay identify the priority of the UCI for the corresponding SPS PDSCH,and the UCI for the SPS PDSCH identified as high priority may beprioritized over the UCI for the PDSCH. In one implementation, if thespecific parameter for identifying the priority is configured inSPS-Config, the UCI for the SPS PDSCH corresponding to the SPS-Configwith the specific parameter may have the same priority as the UCI forthe PDSCH when collision occurs. In one implementation, the configuredparameter may identify the priority of the UCI for the corresponding SPSPDSCH, and the UCI for the SPS PDSCH identified as high priority mayhave the same priority as the UCI for the PDSCH. In one implementation,both UCI for the SPS PDSCH and UCI for the PDSCH may be identified ashigh priority transmissions using different physical identifications andfurther comparison between the priority of UCI for the PDSCH and that ofUCI for the SPS PDSCH may not be necessary.

Case 2-1-4: In one implementation, a field in a DCI format thatindicates activation of the SPS PDSCH may be used to indicate a priorityorder between a PDSCH and an SPS PDSCH. The field may be a new field ora reused field in the DCI format. In one implementation, the new fieldmay include one bit to indicate whether or not the activated SPS PDSCHis prioritized. For example, the bit having a value of ‘1’ may beregarded as ‘a prioritized SPS PDSCH’ (e.g., high priority), whereas thebit having a value of ‘0’ may be regarded as ‘a deprioritized SPS PDSCH’(e.g., low priority transmission). Alternatively, the bit having a valueof ‘0’ may be regarded as ‘a prioritized SPS PDSCH’, whereas the bithaving a value of ‘1’ may be regarded as ‘a deprioritized SPS PDSCH’. Inone implementation, an existing field in the DCI format may be reused.The UE may validate the prioritized SPS PDSCH based on the existingfield in the DCI format. In one implementation, UCI for the SPS PDSCHcorresponding to the DCI with the specific field that indicates thepriority may be prioritized when collision occurs between UCI for thePDSCH and the UCI for the SPS PDSCH. In one implementation, the UCI forthe SPS PDSCH corresponding to the DCI with the specific field may havethe same priority as the UCI for the PDSCH when collision occurs.

Case 2-1-5: The priority may depend on the periodicity scheduled in theSPS configuration (e.g., SPS-Config). In one implementation, if theperiodicity in the SPS-Config is smaller than a threshold value (e.g., 2symbols), UCI for the SPS PDSCH may be prioritized when collision occursbetween UCI for a PDSCH and the UCI for the SPS PDSCH. In oneimplementation, the UCI for the SPS PDSCH with periodicity smaller thanthe threshold value may have the same priority as the UCI for the PDSCHwhen collision occurs.

Case 2-1-6: The priority may depend on a K1 value for an SPS PDSCH. Inone implementation, UCI for a PDSCH transmission with the K1 valuesmaller than a threshold value (e.g., 2 symbols) may be prioritized whencollision occurs between UCI for the PDSCH and UCI for the SPS PDSCH.The K1 value may indicate a time offset between a given PDSCH and thecorresponding HARQ-ACK information. In one implementation, K1 may be thenumber of slots/sub-slots from the slot/sub-slot containing the end ofthe PDSCH to the slot/sub-slot containing the start of the PUCCH withHARQ-ACK information. In one implementation, the UCI for the SPS PDSCHwith the K1 value smaller than the threshold value may have the samepriority as the UCI for the PDSCH when collision occurs.

Implementations described in cases 2-1-1 through 2-1-6 may be a separatemethod respectively or may be combined to form a specific method.

Case 2-2: Collision Between UCI for PDSCH Scheduled by DCI Scrambledwith C-RNTI and UCI for the SPS PDSCH Identified as a Transmission withHigh Priority

In one implementation, UCI for the PDSCH and UCI for the SPS PDSCH mayboth be identified as high priority transmissions using differentphysical identifications. In one implementation, UCI for the PDSCH maybe identified as low priority transmission and UCI for the SPS PDSCH maybe identified as high priority. In one implementation, UCI for the PDSCHmay be identified as high priority using other physical identifications(e.g., a DCI field, a new DCI format) and UCI for the SPS PDSCH may beidentified as the transmission with high priority among UCI foroverlapped multiple active SPS PDSCHs.

Case 2-2-1: In one implementation, multiple active SPS configurationsmay be supported, and each SPS configuration may have a correspondingindex. An SPS PDSCH corresponding to a specific index may be regarded asthe prioritized PDSCH. For example, among three SPS PDSCHs having index0, index 1, and index 2 respectively, the SPS PDSCH with index 0 mayhave the highest priority. In one implementation, the SPS PDSCHcorresponding to a configuration with index 0 may be regarded as theprioritized SPS PDSCH in comparison with an SPS PDSCH corresponding to aconfiguration with index other than 0. The UCI for the SPS PDSCHconfigured with index 0 may be prioritized when collision occurs betweenthe UCI for the PDSCH and the UCI for the SPS PDSCH. The UCI for thePDSCH may be indicated as low priority transmission or high prioritytransmission without using the new-RNTI (e.g., priority indication usinga DCI field or a new DCI format). In one implementation, both the UCIfor the SPS PDSCH with index 0 and the UCI for the PDSCH may be regardedas high priority transmissions, and the priority between the UCIs maynot be necessary.

Case 2-2-2: In one implementation, a priority of UCI for an SPS PDSCHmay be configured by a parameter in an SPS configuration (e.g.,SPS-Config). In one implementation, if the specific parameter foridentifying the priority is configured in SPS-Config (e.g., theparameter indicates whether the priority of the UCI for the SPS PDSCH ishigh or low), the UCI for the SPS PDSCH corresponding to the SPS-Configwith the specific parameter may be prioritized when collision occursbetween UCI for the PDSCH and the UCI for the SPS PDSCH. In oneimplementation, the configured parameter may identify the priority ofthe UCI for the corresponding SPS PDSCH, and the UCI for the SPS PDSCHidentified as high priority may be prioritized over the UCI for thePDSCH. The UCI for the PDSCH may be indicated as low prioritytransmission or high priority transmission (e.g., priority indicationusing a field in DCI or a new DCI format). In one implementation, apriority of the UCI for the PDSCH may be indicated by a field in a DCIformat that schedules the PDSCH reception. The UE may determine whetherto prioritize the UCI for the PDSCH or the UCI for the SPS PDSCH basedon the priority of the respective UCI.

Case 2-2-3: In one implementation, a field in a DCI format thatindicates activation of the SPS PDSCH may be used to indicate a priorityorder between a PDSCH and an SPS PDSCH. The field may be a new field ora reused field in the DCI format. In one implementation, the new fieldmay include one bit to indicate whether or not the activated SPS PDSCHis prioritized. For example, the bit having a value of ‘1’ may beregarded as ‘a prioritized SPS PDSCH’, whereas the bit having a value of‘0’ may be regarded as ‘a deprioritized SPS PDSCH’. Alternatively, thebit having a value of ‘0’ may be regarded as ‘a prioritized SPS PDSCH’,whereas the bit having a value of ‘1’ may be regarded as ‘adeprioritized SPS PDSCH’. In one implementation, an existing field inthe DCI format may be reused. The UE may validate the prioritized SPSPDSCH based on the existing field in the DCI format. In oneimplementation, UCI for the SPS PDSCH corresponding to the DCI with thespecific field that indicates the priority may be prioritized whencollision occurs between UCI for the PDSCH and the UCI for the SPSPDSCH.

Case 2-2-4: The priority may depend on the periodicity scheduled in theSPS configuration (e.g., SPS-Config). In one implementation, if theperiodicity in the SPS-Config is smaller than a threshold value (e.g., 2symbols), UCI for the SPS PDSCH may be prioritized when collision occursbetween UCI for a PDSCH and the UCI for the SPS PDSCH.

Case 2-2-5: The priority may depend on a K1 value for an SPS PDSCH. Inone implementation, UCI for a PDSCH transmission with the K1 valuesmaller than a threshold value (e.g., 2 symbols) may be prioritized whencollision occurs between UCI for the PDSCH and UCI for the SPS PDSCH.

Implementations described in cases 2-2-1 through 2-1-5 may be a separatemethod respectively or may be combined to form a specific method.

FIG. 1 is a flowchart of a method 100 performed by a UE for configuringa priority of UCI for an SPS PDSCH according to an exampleimplementation of the present disclosure. In action 102, the UE mayreceive, from a BS, an RRC configuration to configure a first SPS PDSCH.For example, the RRC configuration may include an IE SPS-Config. The UEmay also receive a DCI format with CRC bits scrambled by CS-RNTI toactivate the first SPS PDSCH. After the first SPS PDSCH is activated,the UE may receive a PDSCH periodically without receiving acorresponding PDCCH. The periodicity of the SPS PDSCH may be indicatedin the RRC configuration.

In action 104, the UE may generate first UCI in response to the firstSPS PDSCH. The first UCI may include HARQ-ACK information for the firstSPS PDSCH, such as ACK/NACK feedback to the BS. The RRC configurationreceived in action 102 may include a first parameter that indicates apriority of the first UCI. The UE may generate a HARQ-ACK codebook thatis associated with the priority indicated by an explicit indication(e.g., the first parameter) in the RRC configuration.

FIG. 2 is a flowchart of a method 200 performed by a UE for configuringa priority of UCI for a PDSCH according to an example implementation ofthe present disclosure. In action 202, the UE may receive, from the BS,a DCI format that schedules a PDSCH reception. The DCI format in action202 may have CRC bits scrambled by C-RNTI. In action 204, the UE maygenerate second UCI in response to the PDSCH reception. The second UCImay include HARQ-ACK information for the PDSCH reception. The DCI formatreceived in action 202 may include a field that indicates a priority ofthe second UCI. The UE may generate a HARQ-ACK codebook that isassociated with the priority indicated by the DCI format.

Action 206 may be optionally performed by the UE. In one implementation,action 206 may be performed by the UE when the first UCI generated inaction 104 in FIG. 1 and the second UCI generated in action 204partially or fully overlap in the time domain (also referred to as UCIcollision). In one implementation, the UCI collision may occur when thefirst UCI and the second UCI are to be transmitted in a same slot. Inaction 206, the UE may transmit, to the BS, one of the first UCI and thesecond UCI based on the priority of the first UCI and the priority ofthe second UCI. For example, the UE may transmit the first UCI if thefirst UCI has a higher priority than the second UCI, and vice versa. Inone implementation, the UE may transmit both the first UCI and thesecond UCI if the first UCI and the second UCI have the same priority.

FIG. 3 is a diagram 300 illustrating a procedure for handling UCIcollision according to an example implementation of the presentdisclosure. In action 332, the UE 310 receives an RRC configuration fromthe BS 320 to configure a SPS PDSCH. In action 334, the UE 310 generatesthe first UCI in response to the SPS PDSCH. In action 336, the UE 310receives a DCI format that schedules a PDSCH. In action 338, the UE 310generates the second UCI in response to the PDSCH. In action 340, the UE310 may transmit a prioritized UCI to the BS 320 based on the priorityof the first UCI and the priority of the second UCI after determiningthat the first UCI and the second UCI partially or fully overlap in thetime domain. Actions shown in FIG. 3 should not be construed asnecessarily order dependent. The order in which the process is describedis not intended to be construed as a limitation. For example, action 338may be performed before action 334 in other implementations. That is,the second UCI may be generated before the first UCI is generated.

It should be noted that UCI collision may also occur between UCI for afirst SPS PDSCH and UCI for a second SPS PDSCH when multiple activatedSPS PDSCH configurations are supported by the UE. In one implementation,the RRC configuration received in action 102 in FIG. 2 may indicate apriority of the first UCI for the first SPS PDSCH and a priority of thesecond UCI for the second SPS PDSCH. The UE may transmit a prioritizedUCI based on the priority of the first UCI and the priority of thesecond UCI when the first UCI for the first SPS PDSCH and the second UCIfor the second SPS PDSCH partially or fully overlap in the time domain.

In one implementation, multiple activated SPS PDSCH configurations maybe supported by the UE, and the UE may need to handle collision betweenmultiple activated SPS PDSCHs. The UE may receive, from the BS, an RRCconfiguration to configure a second SPS PDSCH. In one implementation,the RRC configuration may be the same as that received in action 102 inFIG. 1 for configuring the first SPS PDSCH. The RRC configuration mayinclude a second parameter that indicates a prioritized SPS PDSCH whenthe first SPS PDSCH and the second SPS PDSCH partially or fully overlapin the time domain.

In one implementation, the second parameter may be a specific priorityindex, which may be an integer greater than or equal to 0. An SPS PDSCHassociated with the specific priority index may be regarded as theprioritized PDSCH. In one implementation, the second parameter for theprioritized SPS PDSCH may correspond to index 0. That is, the SPS PDSCHassociated with index 0 may be regarded as the prioritized SPS PDSCH.

FIG. 4 is a block diagram illustrating a node for wireless communicationaccording to the present disclosure. As illustrated in FIG. 4, a node400 may include a transceiver 420, a processor 428, a memory 434, one ormore presentation components 438, and at least one antenna 436. The node400 may also include an RF spectrum band module, a BS communicationsmodule, a network communications module, and a system communicationsmanagement module, Input/Output (I/O) ports, I/O components, and a powersupply (not shown in FIG. 4).

Each of the components may directly or indirectly communicate with eachother over one or more buses 440. The node 400 may be a UE or a BS thatperforms various functions disclosed with reference to FIGS. 1 through3.

The transceiver 420 has a transmitter 422 (e.g.,transmitting/transmission circuitry) and a receiver 424 (e.g.,receiving/reception circuitry) and may be configured to transmit and/orreceive time and/or frequency resource partitioning information. Thetransceiver 420 may be configured to transmit in different types ofsubframes and slots including but not limited to usable, non-usable andflexibly usable subframes and slot formats. The transceiver 420 may beconfigured to receive data and control channels.

The node 400 may include a variety of computer-readable media.Computer-readable media may be any available media that may be accessedby the node 400 and include both volatile and non-volatile media,removable and non-removable media.

The computer-readable media may include computer storage media andcommunication media. Computer storage media include both volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules ordata.

Computer storage media include RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, Digital Versatile Disks (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices. Computer storage media do notinclude a propagated data signal. Communication media typically embodycomputer-readable instructions, data structures, program modules orother data in a modulated data signal such as a carrier wave or othertransport mechanism and include any information delivery media.

The term “modulated data signal” means a signal that has one or more ofits characteristics set or changed in such a manner as to encodeinformation in the signal. Communication media include wired media suchas a wired network or direct-wired connection, and wireless media suchas acoustic, RF, infrared and other wireless media. Combinations of anyof the previously listed components should also be included within thescope of computer-readable media.

The memory 434 may include computer-storage media in the form ofvolatile and/or non-volatile memory. The memory 434 may be removable,non-removable, or a combination thereof. Example memory includessolid-state memory, hard drives, optical-disc drives, etc. Asillustrated in FIG. 4, the memory 434 may store computer-readable,computer-executable instructions 432 (e.g., software codes) that areconfigured to cause the processor 428 to perform various functionsdisclosed herein, for example, with reference to FIGS. 1 through 3.Alternatively, the instructions 432 may not be directly executable bythe processor 428 but be configured to cause the node 400 (e.g., whencompiled and executed) to perform various functions disclosed herein.

The processor 428 (e.g., having processing circuitry) may include anintelligent hardware device, e.g., a Central Processing Unit (CPU), amicrocontroller, an ASIC, etc. The processor 428 may include memory. Theprocessor 428 may process data 430 and the instructions 432 receivedfrom the memory 434, and information transmitted and received via thetransceiver 420, the base band communications module, and/or the networkcommunications module. The processor 428 may also process information tobe sent to the transceiver 420 for transmission via the antenna 436 tothe network communications module for transmission to a core network.

One or more presentation components 438 present data indications to aperson or another device. Examples of presentation components 438include a display device, a speaker, a printing component, and avibrating component, etc.

In view of the present disclosure, it is obvious that various techniquesmay be used for implementing the concepts in the present disclosurewithout departing from the scope of those concepts. Moreover, while theconcepts have been disclosed with specific reference to certainimplementations, a person of ordinary skill in the art may recognizethat changes may be made in form and detail without departing from thescope of those concepts. As such, the disclosed implementations are tobe considered in all respects as illustrative and not restrictive. Itshould also be understood that the present disclosure is not limited tothe particular implementations disclosed and many rearrangements,modifications, and substitutions are possible without departing from thescope of the present disclosure.

What is claimed is:
 1. A user equipment (UE) comprising: one or morenon-transitory computer-readable media containing computer-executableinstructions embodied therein; and at least one processor coupled to theone or more non-transitory computer-readable media, the at least oneprocessor configured to execute the computer-executable instructions to:receive, from a base station (BS), a Radio Resource Control (RRC)configuration to configure a first semi-persistent scheduling (SPS)physical downlink shared channel (PDSCH); and generate first uplinkcontrol information (UCI) in response to the first SPS PDSCH; whereinthe RRC configuration includes a first parameter that indicates apriority of the first UCI.
 2. The UE of claim 1, wherein the at leastone processor is further configured to execute the computer-executableinstructions to: receive, from the BS, a downlink control information(DCI) format that schedules a PDSCH reception; and generate second UCIin response to the PDSCH reception; wherein the DCI format includes afield that indicates a priority of the second UCI.
 3. The UE of claim 2,wherein the first UCI and the second UCI partially or fully overlap in atime domain, and the at least one processor is further configured toexecute the computer-executable instructions to: transmit, to the BS,one of the first UCI and the second UCI based on the priority of thefirst UCI and the priority of the second UCI.
 4. The UE of claim 1,wherein the first UCI includes hybrid automatic repeat requestacknowledgement (HARQ-ACK) information.
 5. The UE of claim 1, whereinthe at least one processor is further configured to execute thecomputer-executable instructions to: receive, from the BS, the RRCconfiguration to configure a second SPS PDSCH; wherein the RRCconfiguration includes a second parameter that indicates a prioritizedSPS PDSCH when the first SPS PDSCH and the second SPS PDSCH partially orfully overlap in a time domain.
 6. The UE of claim 5, wherein the secondparameter for the prioritized SPS PDSCH corresponds to index
 0. 7. Amethod for wireless communication performed by a user equipment (UE),the method comprising: receiving, from a base station (BS), a RadioResource Control (RRC) configuration to configure a firstsemi-persistent scheduling (SPS) physical downlink shared channel(PDSCH); and generating first uplink control information (UCI) inresponse to the first SPS PDSCH; wherein the RRC configuration includesa first parameter that indicates a priority of the first UCI.
 8. Themethod of claim 7, further comprising: receiving, from the BS, adownlink control information (DCI) format that schedules a PDSCHreception; and generating second UCI in response to the PDSCH reception;wherein the DCI format includes a field that indicates a priority of thesecond UCI.
 9. The method of claim 8, wherein the first UCI and thesecond UCI partially or fully overlap in a time domain, and the methodfurther comprising: transmitting, to the BS, one of the first UCI andthe second UCI based on the priority of the first UCI and the priorityof the second UCI.
 10. The method of claim 7, wherein the first UCIincludes hybrid automatic repeat request acknowledgement (HARQ-ACK)information.
 11. The method of claim 7, further comprising: receiving,from the BS, the RRC configuration to configure a second SPS PDSCH;wherein the RRC configuration includes a second parameter that indicatesa prioritized SPS PDSCH when the first SPS PDSCH and the second SPSPDSCH partially or fully overlap in a time domain.
 12. The method ofclaim 11, wherein the second parameter for the prioritized SPS PDSCHcorresponds to index 0.